5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
- Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-6: ILF Keyword Reference

NO INPUT


NO INPUT is used in input processes to prevent a user from modifying a particular field.

    ????? NO INPUT ??? ?????????????????????? ??? (AT APPEARANCE # ???)
    (1)            (2) (3)                    (4)                  (5)

(1) T/F execution conditions
(2) Application ID
(3) Field name or predefined field
(4) Occurrence (constant/index)
(5) Appearance (constant/index)

Using the Statement

The NO INPUT statement can be used to make fields conditionally unmodifiable, depending on prior entries. The appearance number can be used if the same field appears more than once on the image.

The application ID, field name, occurrence, and appearance may all be left blank, in which case the statement is applied to all items on the image.

When NO INPUT is executed for an item, it is dimmed on the image.

Restrictions

NO INPUT statements are only valid on image-related event points.

Related Statements

OK INPUT

Example

The example below prevents the operator from entering a General Ledger account number into a customer's record if the General Ledger Chart of Accounts file does not exist. 

          IF EXIST TGL BALANCE1            FAIL 0
    F     NO INPUT TAR CUSTOMER ACCOUNT           (AT APPEARANCE #    )

Application Design Manual                                         "Powered by Appx Software"

666

©2006 By APPX Software, Inc. All Rights Reserved